MySQL High Availability by Charles Bell & Mats Kindahl & Lars Thalmann

Author:Charles Bell & Mats Kindahl & Lars Thalmann [Charles Bell & Mats Kindahl & Lars Thalmann]
Language: eng
Format: epub
Tags: Reference:Computers
ISBN: 9780596807320
Publisher: O'Reilly Media
Published: 2010-06-27T23:00:00+00:00

Here we see two rows in the result set. The first row tells us the OPTIMIZE TABLE command could not be run and that the command will instead re-create the table and run the ANALYZE TABLE command. The second row is the result of the ANALYZE TABLE step.

Like the ANALYZE TABLE command above, any unusual events during the execution of the command are indicated in the Msg_type field by “info,” “error,” or “warning.” In these cases, the Msg_text field will give you additional information about the event. You should always investigate the situation if you get any result other than “status” and “OK.”

The LOCAL or NO_WRITE_TO_BINLOG keyword prevents the command from being written to the binary log (it will therefore not be replicated in a replication topology). This can be very useful if you want to experiment or tune while replicating data or if you want to omit this step from your binary log and thereby not replay it during PITR.

You should run this command whenever there have been significant updates to the table (e.g., a large number of deletes and inserts). This operation is designed to rearrange data elements into a more optimal structure and could run for longer than expected. This is one operation that is best run during times of lower loads.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.